User interfaces for logging user activities

ABSTRACT

The present disclosure generally relates to logging user activities during a subset of a recurring time period. In some embodiments, based on received physiological data, a computer system enables logging of one or more user activities to be performed during a subset of a recurring time period. In some embodiments, based on performance of the one or more user activities during a subset of a recurring time period, a computer system enables logging of one or more user activities to be performed during a subset of a recurring time period for a predetermined period of time.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Pat. Application Serial No.16/953,781, filed Nov. 20, 2020, entitled a “USER INTERFACES FOR LOGGINGUSER ACTIVITIES,” which claims priority to U.S. Provisional ApplicationSerial No. 63/072,889, filed Aug. 31, 2020, entitled a “USER INTERFACESFOR LOGGING USER ACTIVITIES,” the contents of which is herebyincorporated by reference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for logging user activities during asubset of a recurring time period.

BACKGROUND

Computer systems can include applications for logging user activitiesduring a subset of a recurring time period. Such systems can receiveuser input using user interfaces that include one or more graphicalelements adapted for use with logging user activities during a subset ofa recurring time period.

BRIEF SUMMARY

Some techniques for logging user activities during a subset of arecurring time period using electronic devices, however, are generallycumbersome and inefficient. For example, some existing techniques use acomplex and time-consuming user interface, which may include multiplekey presses or keystrokes. Existing techniques require more time thannecessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for logging useractivities during a subset of a recurring time period. Such methods andinterfaces optionally complement or replace other methods for logginguser activities during a subset of a recurring time period. Such methodsand interfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

In accordance with some embodiments, a method, performed at a computersystem that is in communication with a display generation component andone or more input devices is described. The method includes: displaying,via the display generation component, a task selection user interfacewith a set of one or more selectable task user interface objects, theset of one or more selectable task user interface objects includes: inaccordance with a determination that physiological data for a firstsubset of a recurring time period meets a first set of criteria, a firstselectable task user interface object that corresponds to a first typeof user activity to be performed during the first subset of therecurring time period; and in accordance with a determination thatphysiological data for a second subset of the recurring time period,different from the first subset of the recurring time period, meets thefirst set of criteria, a second selectable task user interface objectthat corresponds to a second type of user activity to be performedduring the second subset of the recurring time period; while displayingthe task selection user interface, receiving, via the one or more inputdevices, a first set of one or more inputs; and in response to thereceiving the first set of one or more inputs: in accordance with adetermination that the first set of one or more inputs includes an inputselecting the first selectable task user interface object, enablinglogging of the first type of user activity during the first subset ofthe recurring time period; and in accordance with a determination thatthe first set of one or more inputs includes an input selecting thesecond selectable task user interface object, enabling logging of thesecond type of user activity during the second subset of the recurringtime period.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a computer system that is in communicationwith a display generation component and one or more input devices isdescribed. The one or more programs include instructions for:displaying, via the display generation component, a task selection userinterface with a set of one or more selectable task user interfaceobjects, the set of one or more selectable task user interface objectsincludes: in accordance with a determination that physiological data fora first subset of a recurring time period meets a first set of criteria,a first selectable task user interface object that corresponds to afirst type of user activity to be performed during the first subset ofthe recurring time period; and in accordance with a determination thatphysiological data for a second subset of the recurring time period,different from the first subset of the recurring time period, meets thefirst set of criteria, a second selectable task user interface objectthat corresponds to a second type of user activity to be performedduring the second subset of the recurring time period; while displayingthe task selection user interface, receiving, via the one or more inputdevices, a first set of one or more inputs; and in response to thereceiving the first set of one or more inputs: in accordance with adetermination that the first set of one or more inputs includes an inputselecting the first selectable task user interface object, enablinglogging of the first type of user activity during the first subset ofthe recurring time period; and in accordance with a determination thatthe first set of one or more inputs includes an input selecting thesecond selectable task user interface object, enabling logging of thesecond type of user activity during the second subset of the recurringtime period.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a computer system that is in communicationwith a display generation component and one or more input devices isdescribed. The one or more programs include instructions for:displaying, via the display generation component, a task selection userinterface with a set of one or more selectable task user interfaceobjects, the set of one or more selectable task user interface objectsincludes: in accordance with a determination that physiological data fora first subset of a recurring time period meets a first set of criteria,a first selectable task user interface object that corresponds to afirst type of user activity to be performed during the first subset ofthe recurring time period; and in accordance with a determination thatphysiological data for a second subset of the recurring time period,different from the first subset of the recurring time period, meets thefirst set of criteria, a second selectable task user interface objectthat corresponds to a second type of user activity to be performedduring the second subset of the recurring time period; while displayingthe task selection user interface, receiving, via the one or more inputdevices, a first set of one or more inputs; and in response to thereceiving the first set of one or more inputs: in accordance with adetermination that the first set of one or more inputs includes an inputselecting the first selectable task user interface object, enablinglogging of the first type of user activity during the first subset ofthe recurring time period; and in accordance with a determination thatthe first set of one or more inputs includes an input selecting thesecond selectable task user interface object, enabling logging of thesecond type of user activity during the second subset of the recurringtime period.

In accordance with some embodiments, a computer system is described. Thecomputer system includes: a display generation component; one or moreinput devices; one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors. Theone or more programs include instructions for: displaying, via thedisplay generation component, a task selection user interface with a setof one or more selectable task user interface objects, the set of one ormore selectable task user interface objects includes: in accordance witha determination that physiological data for a first subset of arecurring time period meets a first set of criteria, a first selectabletask user interface object that corresponds to a first type of useractivity to be performed during the first subset of the recurring timeperiod; and in accordance with a determination that physiological datafor a second subset of the recurring time period, different from thefirst subset of the recurring time period, meets the first set ofcriteria, a second selectable task user interface object thatcorresponds to a second type of user activity to be performed during thesecond subset of the recurring time period; while displaying the taskselection user interface, receiving, via the one or more input devices,a first set of one or more inputs; and in response to the receiving thefirst set of one or more inputs: in accordance with a determination thatthe first set of one or more inputs includes an input selecting thefirst selectable task user interface object, enabling logging of thefirst type of user activity during the first subset of the recurringtime period; and in accordance with a determination that the first setof one or more inputs includes an input selecting the second selectabletask user interface object, enabling logging of the second type of useractivity during the second subset of the recurring time period.

In accordance with some embodiments, a computer system, including adisplay generation component and one or more input devices is described.The computer system also includes: means for displaying, via the displaygeneration component, a task selection user interface with a set of oneor more selectable task user interface objects, the set of one or moreselectable task user interface objects includes: in accordance with adetermination that physiological data for a first subset of a recurringtime period meets a first set of criteria, a first selectable task userinterface object that corresponds to a first type of user activity to beperformed during the first subset of the recurring time period; and inaccordance with a determination that physiological data for a secondsubset of the recurring time period, different from the first subset ofthe recurring time period, meets the first set of criteria, a secondselectable task user interface object that corresponds to a second typeof user activity to be performed during the second subset of therecurring time period; means for, while displaying the task selectionuser interface, receiving, via the one or more input devices, a firstset of one or more inputs; and means for, in response to the receivingthe first set of one or more inputs: in accordance with a determinationthat the first set of one or more inputs includes an input selecting thefirst selectable task user interface object, enabling logging of thefirst type of user activity during the first subset of the recurringtime period; and in accordance with a determination that the first setof one or more inputs includes an input selecting the second selectabletask user interface object, enabling logging of the second type of useractivity during the second subset of the recurring time period.

In accordance with some embodiments, a method, performed at a computersystem that is in communication with a display generation component andone or more input devices is described. The method includes: displaying,via the display generation component, a goal creation user interfacewith a set of one or more selectable goal creation user interfaceobjects, the set of one or more selectable goal creation user interfaceobjects includes: in accordance with a determination that a first typeof user activity performed for a first subset of a recurring time periodmeets a first set of criteria, a first selectable goal creation userinterface object that corresponds to the first type of user activity tobe performed during the first subset of the recurring time period; andin accordance with a determination that a second type of user activityperformed for a second subset of a recurring time period, different fromthe first subset of the recurring time period, meets a first set ofcriteria, a second selectable goal creation user interface object thatcorresponds to the second type of user activity to be performed duringthe second subset of the recurring time period; while displaying thegoal creation user interface, receiving a first set of one or moreinputs; and in response to the receiving the first set of one or moreinputs: in accordance with a determination that the first set of one ormore inputs includes an input selecting the first selectable goalcreation user interface object, enabling logging of the first type ofuser activity during the first subset of the recurring time period for apredetermined duration of time; and in accordance with a determinationthat the first set of one or more inputs includes an input selecting thesecond selectable goal creation user interface object, enabling loggingof the second type of user activity during the second subset of therecurring time period for the predetermined duration of time.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a computer system that is in communicationwith a display generation component and one or more input devices isdescribed. The one or more programs include instructions for:displaying, via the display generation component, a goal creation userinterface with a set of one or more selectable goal creation userinterface objects, the set of one or more selectable goal creation userinterface objects includes: in accordance with a determination that afirst type of user activity performed for a first subset of a recurringtime period meets a first set of criteria, a first selectable goalcreation user interface object that corresponds to the first type ofuser activity to be performed during the first subset of the recurringtime period; and in accordance with a determination that a second typeof user activity performed for a second subset of a recurring timeperiod, different from the first subset of the recurring time period,meets a first set of criteria, a second selectable goal creation userinterface object that corresponds to the second type of user activity tobe performed during the second subset of the recurring time period;while displaying the goal creation user interface, receiving a first setof one or more inputs; and in response to the receiving the first set ofone or more inputs: in accordance with a determination that the firstset of one or more inputs includes an input selecting the firstselectable goal creation user interface object, enabling logging of thefirst type of user activity during the first subset of the recurringtime period for a predetermined duration of time; and in accordance witha determination that the first set of one or more inputs includes aninput selecting the second selectable goal creation user interfaceobject, enabling logging of the second type of user activity during thesecond subset of the recurring time period for the predeterminedduration of time.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of a computer system that is in communicationwith a display generation component and one or more input devices isdescribed. The one or more programs include instructions for:displaying, via the display generation component, a goal creation userinterface with a set of one or more selectable goal creation userinterface objects, the set of one or more selectable goal creation userinterface objects includes: in accordance with a determination that afirst type of user activity performed for a first subset of a recurringtime period meets a first set of criteria, a first selectable goalcreation user interface object that corresponds to the first type ofuser activity to be performed during the first subset of the recurringtime period; and in accordance with a determination that a second typeof user activity performed for a second subset of a recurring timeperiod, different from the first subset of the recurring time period,meets a first set of criteria, a second selectable goal creation userinterface object that corresponds to the second type of user activity tobe performed during the second subset of the recurring time period;while displaying the goal creation user interface, receiving a first setof one or more inputs; and in response to the receiving the first set ofone or more inputs: in accordance with a determination that the firstset of one or more inputs includes an input selecting the firstselectable goal creation user interface object, enabling logging of thefirst type of user activity during the first subset of the recurringtime period for a predetermined duration of time; and in accordance witha determination that the first set of one or more inputs includes aninput selecting the second selectable goal creation user interfaceobject, enabling logging of the second type of user activity during thesecond subset of the recurring time period for the predeterminedduration of time.

In accordance with some embodiments, a computer system is described. Thecomputer system includes: a display generation component; one or moreinput devices; one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors. Theone or more programs include instructions for: displaying, via thedisplay generation component, a goal creation user interface with a setof one or more selectable goal creation user interface objects, the setof one or more selectable goal creation user interface objects includes:in accordance with a determination that a first type of user activityperformed for a first subset of a recurring time period meets a firstset of criteria, a first selectable goal creation user interface objectthat corresponds to the first type of user activity to be performedduring the first subset of the recurring time period; and in accordancewith a determination that a second type of user activity performed for asecond subset of a recurring time period, different from the firstsubset of the recurring time period, meets a first set of criteria, asecond selectable goal creation user interface object that correspondsto the second type of user activity to be performed during the secondsubset of the recurring time period; while displaying the goal creationuser interface, receiving a first set of one or more inputs; and inresponse to the receiving the first set of one or more inputs: inaccordance with a determination that the first set of one or more inputsincludes an input selecting the first selectable goal creation userinterface object, enabling logging of the first type of user activityduring the first subset of the recurring time period for a predeterminedduration of time; and in accordance with a determination that the firstset of one or more inputs includes an input selecting the secondselectable goal creation user interface object, enabling logging of thesecond type of user activity during the second subset of the recurringtime period for the predetermined duration of time.

In accordance with some embodiments, a computer system including adisplay generation component and one or more input devices is described.The computer system also includes: means for displaying, via the displaygeneration component, a goal creation user interface with a set of oneor more selectable goal creation user interface objects, the set of oneor more selectable goal creation user interface objects includes: inaccordance with a determination that a first type of user activityperformed for a first subset of a recurring time period meets a firstset of criteria, a first selectable goal creation user interface objectthat corresponds to the first type of user activity to be performedduring the first subset of the recurring time period; and in accordancewith a determination that a second type of user activity performed for asecond subset of a recurring time period, different from the firstsubset of the recurring time period, meets a first set of criteria, asecond selectable goal creation user interface object that correspondsto the second type of user activity to be performed during the secondsubset of the recurring time period; means for, while displaying thegoal creation user interface, receiving a first set of one or moreinputs; and means for, in response to the receiving the first set of oneor more inputs: in accordance with a determination that the first set ofone or more inputs includes an input selecting the first selectable goalcreation user interface object, enabling logging of the first type ofuser activity during the first subset of the recurring time period for apredetermined duration of time; and in accordance with a determinationthat the first set of one or more inputs includes an input selecting thesecond selectable goal creation user interface object, enabling loggingof the second type of user activity during the second subset of therecurring time period for the predetermined duration of time.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for logging user activities during a subset of a recurringtime period, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for logging user activities during asubset of a recurring time period.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6AL illustrate exemplary user interfaces for logging useractivities during a subset of a recurring time period, in accordancewith some embodiments.

FIG. 7 is a flow diagram illustrating a method for logging useractivities during a subset of a recurring time period, in accordancewith some embodiments.

FIGS. 8A-8B are a flow diagram illustrating a method for logging useractivities during a subset of a recurring time period, in accordancewith some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for logging user activities during a subset of arecurring time period. Further, electronic devices should providedisplays of logged user activities during a subset of a recurring timeperiod along with other user data in order for a user to determine theeffects of performing user activities. Such techniques can reduce thecognitive burden on a user who log user activities during a subset of arecurring time period, thereby enhancing productivity. Further, suchtechniques can reduce processor and battery power otherwise wasted onredundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6AL illustrate exemplary user interfaces logginguser activities during a subset of a recurring time period. FIG. 7 is aflow diagram illustrating methods of logging user activities during asubset of a recurring time period, in accordance with some embodiments.FIGS. 8A-8B are a flow diagram illustrating methods of logging useractivities during a subset of a recurring time period, in accordancewith some embodiments. The user interfaces in FIGS. 6A-6AL are used toillustrate the processes described below, including the processes inFIG. 7 and FIGS. 8A-8B.

Although the following description uses terms "first," "second," etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms "a," "an," and "the" are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term "and/or" as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,”“including,” “comprises,” and/or“comprising," when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean "upondetermining" or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click" of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2 ) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2 ). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures) asinput. In some embodiments, the one or more input devices are integratedwith the computer system. In some embodiments, the one or more inputdevices are separate from the computer system.

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. Pat. Application11/322,549, "Unlocking a Device by Performing Gestures on an UnlockImage," filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is herebyincorporated by reference in its entirety. A longer press of the pushbutton (e.g., 206) optionally turns power to device 100 on or off. Thefunctionality of one or more of the buttons are, optionally,user-customizable. Touch screen 112 is used to implement virtual or softbuttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed "graphics"). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat.: 6,323,846 (Westerman et al.), 6,570,557(Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Pat.Publication 2002/0015024A1, each of which is hereby incorporated byreference in its entirety. However, touch screen 112 displays visualoutput from device 100, whereas touch-sensitive touchpads do not providevisual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. Pat. Application No.11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006;(2) U.S. Pat. Application No. 10/840,862, “Multipoint Touchscreen,”filed May 6, 2004; (3) U.S. Pat. Application No. 10/903,964, "GesturesFor Touch Sensitive Input Devices," filed Jul. 30, 2004; (4) U.S. Pat.Application No. 11/048,264, “Gestures For Touch Sensitive InputDevices,” filed Jan. 31, 2005; (5) U.S. Pat Application No. 11/038,590,“Mode-Based Graphical User Interfaces For Touch Sensitive InputDevices,” filed Jan. 18, 2005; (6) U.S. Pat Application No. 11/228,758,“Virtual Input Device Placement On A Touch Screen User Interface,” filedSept. 16, 2005; (7) U.S. Pat Application No. 11/228,700, “Operation Of AComputer With A Touch Screen Interface,” filed Sept. 16, 2005; (8) U.S.Pat Application No. 11/228,737, “Activating Virtual Keys Of ATouch-Screen Virtual Keyboard,” filed Sept. 16, 2005; and (9) U.S. PatApplication No. 11/367,749, “Multi-Functional Hand-Held Device,” filedMar. 3, 2006. All of these applications are incorporated by referenceherein in their entirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. Pat Application Nos. 11/241,839,“Proximity Detector In Handheld Device”; 11/240,788, “Proximity DetectorIn Handheld Device”; 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; 11/586,862, “Automated Response To And SensingOf User Activity In Portable Devices”; and 11/638,251, “Methods AndSystems For Automatic Configuration Of Peripherals,” which are herebyincorporated by reference in their entirety. In some embodiments, theproximity sensor turns off and disables touch screen 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Pat Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Pat Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   Contacts module 137 (sometimes called an address book or contact    list);-   Telephone module 138;-   Video conference module 139;-   E-mail client module 140;-   Instant messaging (IM) module 141;-   Workout support module 142;-   Camera module 143 for still and/or video images;-   Image management module 144;-   Video player module;-   Music player module;-   Browser module 147;-   Calendar module 148;-   Widget modules 149, which optionally include one or more of: weather    widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm    clock widget 149-4, dictionary widget 149-5, and other widgets    obtained by the user, as well as user-created widgets 149-6;-   Widget creator module 150 for making user-created widgets 149-6;-   Search module 151;-   Video and music player module 152, which merges video player module    and music player module;-   Notes module 153;-   Map module 154; and/or-   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, "instant messaging"refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatApplication No. 60/936,562, "Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos," filed Jun. 20,2007, and U.S. Pat Application No. 11/968,067, "Portable MultifunctionDevice, Method, and Graphical User Interface for Playing Online Videos,"filed Dec. 31, 2007, the contents of which are hereby incorporated byreference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a "menubutton" is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as"home" or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   Signal strength indicator(s) 402 for wireless communication(s), such    as cellular and Wi-Fi signals;-   Time 404;-   Bluetooth indicator 405;-   Battery status indicator 406;-   Tray 408 with icons for frequently used applications, such as:    -   Icon 416 for telephone module 138, labeled “Phone,” which        optionally includes an indicator 414 of the number of missed        calls or voicemail messages;    -   Icon 418 for e-mail client module 140, labeled “Mail,” which        optionally includes an indicator 410 of the number of unread        e-mails;    -   Icon 420 for browser module 147, labeled “Browser;” and    -   Icon 422 for video and music player module 152, also referred to        as iPod (trademark of Apple Inc.) module 152, labeled “iPod;”        and-   Icons for other applications, such as:    -   Icon 424 for IM module 141, labeled “Messages;”    -   Icon 426 for calendar module 148, labeled “Calendar;”    -   Icon 428 for image management module 144, labeled “Photos;”    -   Icon 430 for camera module 143, labeled “Camera;”    -   Icon 432 for online video module 155, labeled “Online Video;”    -   Icon 434 for stocks widget 149-2, labeled “Stocks;”    -   Icon 436 for map module 154, labeled “Maps;”    -   Icon 438 for weather widget 149-1, labeled “Weather;”    -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”    -   Icon 442 for workout support module 142, labeled “Workout        Support;”    -   Icon 444 for notes module 153, labeled “Notes;” and    -   Icon 446 for a settings application or module, labeled        “Settings,” which provides access to settings for device 100 and        its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Pat Application SerialNo. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3 . Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700-800(FIGS. 7, 8A-8B). A computer-readable storage medium can be any mediumthat can tangibly contain or store computer-executable instructions foruse by or in connection with the instruction execution system,apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector" so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user’s intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6AL illustrate exemplary user interfaces for logging useractivities during a subset of a recurring time period, in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 7 and 8A-8B.

FIG. 6A illustrates electronic device 600 (e.g., a smart phone)displaying introductory user interface 606 on touchscreen display 602.In some embodiments, device 600 includes one or more features of devices100, 300, and/or 500. The current date is August 1, as indicated by thetext (which is provided to improve understanding and is not part of thedisplayed interface) above device 600, and the current time is 08:00, asshown by time indication 604. Introductory user interface 606 introducesthe glucose monitoring feature and includes continue affordance 606 a.In some embodiments, introductory user interface 606 includes multiple,separate screens of content that describe the glucose monitoring featurein greater detail during onboarding. In some embodiments, device 600receives one or more inputs to initiate and complete onboarding for theglucose monitoring feature. In this example, device 600 detects tapinput 608 corresponding to selection of continue affordance 606 a and,in response to receiving tap input 608, device 600 starts the baselinephase (e.g., an onboarding phase, initial phase, and/or sensor phase)and displays hourly log user interface 610, as shown in FIG. 6B.

FIG. 6B depicts device 600 displaying, on touchscreen display 602,hourly log user interface 610. Hourly log user interface 610 includesgraph region 612, which includes day of the week indicators 612 a (e.g.,“S” for Sunday,“M” for Monday, and so forth) and chart region 612 b,which currently reads“NO CHART DATA AVAILABLE.” In some embodiments,once enough data has been received, day of the week indicators 612 a canbe selected, causing device 600 to display chart data for the selectedday. In some embodiments, chart data becomes available after apredetermined amount of data (e.g., blood glucose data) has beenreceived by device 600. In some embodiments, the blood glucose data isprovided by a continuous blood glucose monitor, worn by a user of device600, that is in communication with device 600.

Hourly log user interface 610 further includes log region 614. Logregion 614 includes meal logging affordance 614 a, activity loggingaffordance 614 b, and mood logging affordance 614 c. Hourly log userinterface 610 also includes hours tab affordance 616 a and settings tabaffordance 616 b. In some embodiments, selection of setting tabaffordance 616 b causes device 600 to display a settings user interface.In some embodiments, the settings user interface includes a variety ofoptions, some of which could be reviewing collected data, adjusting timeframes, viewing policies, customizing measurement units.

As shown by time indication 604 in FIG. 6C, 4 hours have passed(relative to FIG. 6B) and the current time is now 12:00. Device 600 hasreceived blood glucose data to be displayed on touchscreen display 602within hourly log user interface 610. The day of the week indicator 612a corresponding to Saturday, August 1 (e.g., “S”) now includes a smallchart icon indicating that data has been collected for the day. Chartregion 612 b now includes hours along the x-axis and blood glucoseamount along the y-axis. Chart line 612 c (e.g., corresponding to bloodglucose measurements) shows the measurements of blood glucose atparticular time periods. Chart line 612 c stops at 12:00, indicatingthat data has been collected prior to 12:00. Chart line 612 c showsstandard blood glucose measurements and elevated blood glucosemeasurements. As illustrated, elevated measurements (e.g., measurementsthat exceed a predetermined threshold value (e.g., >130 mg/dL; >180mg/dL)) are visually distinguished (e.g., in a different line weight, ina different color) from standard measurements. In some embodiments,chart line 612 c does not visually distinguish elevated measurementsfrom standard measurements. Device 600 receives tap input 617corresponding to selection of meal logging affordance 614 a. In responseto detecting tap input 617 at meal logging affordance 614 a, device 600initiates creation of a log entry for a meal (e.g., consumption of foodor beverage (e.g., breakfast, lunch, dinner, a snack)). In someembodiments, selection of activity logging affordance 614 b initiatescreation of a log entry for a physical activity (e.g., exercise,meditation). In some embodiments, selection of mood logging affordance614 c initiates creation of a log entry for a sentiment (e.g., happy,sad, lethargic, energized).

In FIG. 6D, device 600 displays, on touchscreen display 602, log entrycreation user interface 618. Log entry creation user interface 618includes a time selection affordance 618 a. In some embodiments,selection of the time selection affordance 618 a allows customization ofthe time corresponding to the log entry. In this example, time selectionaffordance 618 a shows (e.g., defaults to) the current time of 12:00.Log entry creation user interface 618 also includes search bar 618 b,which can be selected to initiate searching for a particular food. Insome embodiments, when logging an activity or mood, search bar 618 b canbe used to find specific exercises or sentiment. Log entry creation userinterface 618 further includes camera affordance 618 c and saveaffordance 618 d. In some embodiments, selection of camera affordance618 c opens the camera of device 600 and allows a user to capture apicture of their meal. In such embodiments, device 600 generates a logentry based on a photo of a meal (e.g., using image recognitionsoftware).

Log entry creation user interface 618 includes item selection region620. In this example, item selection region 620 displays common foodsthat a user can select for logging. In some embodiments, when logging anactivity, item selection region 620 includes selectable affordancescorresponding to various activities (e.g., walking, biking, meditating).In some embodiments, when logging a mood, item selection region 620includes selectable affordances corresponding to variousmoods/sentiments (e.g., feelings (e.g., anxious, excited, tired)).Device 600 receives tap inputs 622 a and 622 b corresponding toselection of bread affordance 620 a and salad affordance 620 b,respectively. In some embodiments, only one selectable affordance withinthe item selection region 620 can be selected while creating a logentry. In some embodiments, one or more selectable affordance within theitem selection region 620 can be selected while creating a log entry. Asshown in FIG. 6E, in response to detecting tap inputs 622 a and 622 b,device 600 displays log entry creation user interface 618 with breadaffordance 620 a and salad affordance 620 b visually different (e.g.,bolded) than the other food affordances, indicating these two foods havebeen selected for logging.

In FIG. 6E, device 600 receives tap input 624 corresponding to selectionof save affordance 618 d. In response to detecting tap input 624, device600 generates log entry 614 d displayed in in log region 614 of hourlylog user interface 610, as shown in FIG. 6F.

In FIG. 6F, hourly log user interface 610 now includes display of logentry 614 d. Log entry 614 d includes the foods consumed (e.g., breadand salad) and time indication (e.g., 12:00) corresponding to the timethe foods were consumed. Log entry 614 d is displayed below “AFTERNOON,”which indicates the general time period that the meal was consumed. Inthis example, each day is divided into four recurring periods of time(e.g., quadrants), which include morning (04:00 to 10:00), afternoon(10:00 to 16:00), evening (16:00 to 22:00), and overnight (22:00 to04:00). In some embodiments, the quadrants span different ranges oftime. In some embodiments, the quadrants are not equal periods of timewithin a 24-hour period (e.g., two 5-hour periods and two 7-hourperiods; longer period of time for the overnight quadrant). In someembodiments, the subsets of a recurring time period are different thanquadrants (e.g., the day is divided into sextants or octants or a weekis divided into individual days). In some embodiments, a full day is therecurring period of time, without further divisions. In someembodiments, the recurring periods of time are selected (e.g.,customized) by the user. Log entry 614 d further includes optionaldetails that specify the type of food (e.g., “SOURDOUGH ROLL” is a typeof “BREAD”). In this example, “SOURDOUGH ROLL” has been specified below“BREAD” and selectable “ADD DETAIL...” is displayed below “SALAD”as aprompt to add details (e.g., notes, specify the type of salad). In someembodiments, selecting “ADD DETAIL...” causes device 600 to display atext entry field and a keyboard. In some embodiments, after input ofadditional details, device 600 ceases display of “ADD DETAIL...” anddisplays the inputted text. Log entry 614 d optionally includes aselectable affordance 614d1 (e.g., icon with the three dots) to viewdetails and edit (e.g., add or remove types of food) or delete the logentry. In some embodiments, in response to selecting affordance 614d1orlog entry 614 d, device 600 displays a log detail user interfacecontaining specific details about the log entry (e.g., a glucose graph,date, time, and options to edit, duplicate, or delete the log entry).

In addition to generating log entry 614 d, device 600 displays mealglyph 612 d along chart line 612 c. Meal glyph 612 d is displayed at atime, e.g.,12:00, along chart region 612 b, corresponding to the timethat the meal was consumed. In some embodiments, if the log entry was anactivity or mood log entry, a corresponding activity or mood glyph wouldbe displayed along chart line 612 c. In some embodiments, meal,activity, and mood glyphs are selectable user interface objects, that,when selected, causes device 600 to display a log detail user interfacecorresponding to the log entry.

Turning now to FIG. 6G, the current date is August 10, as indicatedabove device 600. Device 600 displays, on touchscreen display 602,hourly log user interface 610. Hourly log user interface 610 includeschart region 612 b with chart line 612 e and activity glyph 614 edisplayed in log region 614. Activity glyph 612 e corresponds to logentry 614 e (e.g., walking). In some embodiments, device 600 can receiveswipe inputs corresponding to chart region 612 b to scroll (e.g.,horizontally scroll) and view previously collected data. In someembodiments, previously collected data within chart region 612 bincludes meal glyphs along chart line 612 c at the times correspondingto each log entry for a morning meal (e.g., toast) and an afternoon meal(e.g., pasta), as shown in log region 614.

Ten days after onboarding, on August 11, as shown in FIG. 6H, device 600displays action notification 626 over hourly log user interface 610.Action notification 626 indicates that the baseline phase is nowcomplete and next phase (e.g., the action phase) of the glucosemonitoring feature is available. In some embodiments, actionnotification 626 is displayed after a minimum amount of time has passedsince the start of the baseline phase (e.g., starting data collection).In some embodiments, action notification 626 is displayed after enoughphysiological data (e.g., blood glucose measurements) have been receivedby device 600. In some embodiments, action notification 626 is displayedafter enough elevated blood glucose measurements have been received bydevice 600. In some embodiments, the action phase is unavailable (e.g.,locked) until a criteria, such as the ones described, have been met.Action notification 626 includes continue affordance 626 a (e.g.,“CHOOSE ACTION ITEMS”). Device 600 detects tap input 628 correspondingto selection of continue affordance 626 a, and in response to tap input628, device 600 initiates action phase set up.

As shown in FIG. 6I, in response to detecting tap input 628, device 600initiates action phase set up by displaying, on touchscreen display 602,baseline summary user interface 630. Baseline summary user interface 630includes an informational affordance 630 a, which details howphysiological data (e.g., blood glucose data) received by device 600 ispresented, and continue affordance 630 b. Informational affordance 630 aincludes elevation values (e.g., one through ten) corresponding to theelevation level (e.g., no elevation, minor elevation, some elevation,elevated, very elevated) of a received blood glucose measurement. Insome embodiments, elevation values are presented instead ofconcentration values (e.g., mg/dL). In some embodiments, elevationvalues are based on (e.g., derived from) blood glucose measurements overa period of time (e.g., from 10:00 to 16:00; a day; every day for sevendays from 09:00 to 12:00).

Baseline summary user interface 630 of FIG. 6I further includes morningbaseline affordance 632. Morning baseline affordance 632 shows morningbaseline graph 632 a, which is a visual representation of elevated datareceived by device 600 during morning quadrant (e.g., period of time inthe morning (e.g., from 04:00 to 10:00)) during the baseline phase(e.g., onboarding phase, initial phase, sensor phase), and morningelevation value 632 b. In some embodiments, morning baseline graph 632 adepicts the instance (e.g., the single morning (e.g., the morning ofAugust 8^(th))) having the most elevated physiological data received bydevice 600 during the morning quadrant of the baseline phase. In someembodiments, morning baseline graph 632 a is based on (e.g., derivedfrom) all physiological data (e.g., displayed as an average) received bydevice 600 during the morning quadrant of the baseline phase (e.g.,lasting 10 days; for a week). In some embodiments, baseline summary userinterface 630 presents subsets of a recurring time period (e.g., a day;a week) different than quadrants (e.g., the day is divided into sextantsor octants or a week is divided into individual days).

As shown in FIG. 6I, device 600 detects swipe input 638, correspondingto a request to scroll baseline summary user interface 630, ontouchscreen display 602. In response to receiving swipe input 638,device 600 displays a second portion of baseline summary user interface630, as shown in FIG. 6J. In FIG. 6J, baseline summary user interface630 includes a portion of morning baseline affordance 632, along with aselectable view all morning data affordance 632 c. In some embodiments,selection of view all morning data affordance 632 c causes device 600 todisplay a user interface having one or more graphs, including morningbaseline graph 632 a, corresponding to physiological data (e.g., bloodglucose measurements) received by device 600 during the morning quadrant(e.g., period of time in the morning (e.g., from 04:00 to 10:00)) of thebaseline phase. In some embodiments, in response to selection of viewall morning data affordance 632 c, device 600 displays graphscorresponding to instances of receiving elevated physiological data(e.g., measurements above a threshold).

In FIG. 6J, baseline summary user interface 630 includes eveningbaseline affordance 634. Evening baseline affordance 634 is analogous tomorning baseline affordance 632, however, evening baseline affordance634 corresponds to physiological data (e.g., blood glucose measurements)received by device 600 during the evening quadrant (e.g., period of timeduring the evening (e.g., from 16:00 to 22:00)) of the baseline phase.Evening baseline affordance 634 includes evening baseline graph 634 a,which shows the period of time during the evening (e.g., from 16:00 to22:00) along the x-axis and blood glucose measurements received bydevice 600 along the y-axis. Portions of evening baseline graph 634 acontaining elevated measurements are visually distinct (e.g., having athicker line weight) from non-elevated measurements. Evening baselineaffordance 634 includes evening elevation value 632 b. Baseline summaryuser interface 630 includes selectable view all evening data affordance634 c, which is analogous to selectable view all morning data affordance632 c.

Baseline summary user interface 630 further includes a portion ofovernight baseline affordance 636, which in analogous to morningbaseline affordance 632 and evening baseline affordance 634. Overnightbaseline affordance 636 corresponds to physiological data (e.g., bloodglucose measurements) received by device 600 during the overnightquadrant (e.g., period of time overnight (e.g., from 22:00 to 04:00)) ofthe baseline phase. In some embodiments, after receiving a scroll input,device 600 displays baseline summary user interface 630 showing theentire overnight baseline affordance 636 and a selectable view allovernight data affordance, analogous to selectable view all morning dataaffordance 632 c and selectable view all evening data affordance 634 c.

In the example described, device 600 displays affordances correspondingto physiological data received during the morning, evening, andovernight quadrants during the baseline phase (e.g., an initial periodof time (e.g., ten days, a week)) and does not display an affordancecorresponding to physiological data received during the afternoonquadrant (e.g., period of time in the afternoon (e.g., from 10:00 to16:00)). In some embodiments, device 600 determines, based on thereceived physiological data, the one or more portions of the day havingthe most elevated blood glucose measurements (e.g., during the baselinephase) and displays baseline affordances accordingly. In someembodiments, the portions of the day having the most elevated bloodglucose measurements, and therefore are displayed by device 600, containthe highest measurements (e.g., the three highest measurements asbetween the four quadrants of the day). In some embodiments, theportions of the day that are displayed by device 600 have the highestelevation values. In some embodiments, the portions of the day that aredisplayed by device 600 have more time spent in an elevated measurementstate. Therefore, in some embodiments, device 600 displays a combinationof the morning, afternoon, evening, and overnight quadrants. In someembodiments, device 600 displays affordances corresponding to eachquadrant (e.g., morning, afternoon, evening, overnight).

As shown in FIG. 6J, device 600 receives tap input 640 corresponding toselection of continue affordance 630 b. In response to detecting tapinput 640, device 600 displays, on touchscreen display 602, taskselection user interface 642, as shown in FIG. 6K. Task selection userinterface 642 currently includes morning task affordance 644, eveningtask affordance 646, and a portion of overnight task affordance 648.Each task affordance (e.g., 644, 646, 648) includes a number ofselectable tasks (e.g., three) to be chosen to be performed during thespecified part of the day (e.g., morning, evening). The selectable tasksare to perform either a physical activity (e.g., “TRY AN ACTIVITY AROUNDBREAKFAST”) or consume or forgo consumption of a type of food (e.g.,“EAT CARBS DURING DINNER”; “AVOID SNACKS AROUND DINNER”) during thespecified part of the day. In some embodiments, the tasks presented toaffect elevated blood glucose measurements are the same for each user(e.g., standard tasks). In some embodiments, performance of these taskshas a positive effect on (e.g., reduces elevation of) blood glucosemeasurements. Device 600 receives swipe input 650 corresponding to arequest to scroll task selection user interface 642.

In response to detecting swipe input 650, device 600 displays anotherportion of task selection user interface 642, as shown in FIG. 6L. Taskselection user interface 642 shows a portion of morning task affordance644, along with evening task affordance 646 and overnight taskaffordance 648. Evening task affordance 646 includes three selectabletasks 646 a-646 c to be performed to affect blood glucose measurementsreceived by device 600 during the evening. Overnight task affordance 648includes three selectable tasks 648 a-648 c to be performed to affectblood glucose measurements received by device 600 overnight. Selectabletask 646 a (which reads, “TRY AN ACTIVITY DURING DINNER”) is a task tobe performed during the evening quadrant (e.g., period of time duringthe evening (e.g., from 16:00 to 22:00)) to affect blood glucosemeasurements received by device 600 during the same period of time.Selectable task 648 b (which reads, “TRY SMALLER PORTIONS OF HIGHRESPONSE FOODS AT DINNER”) is a task to be performed at dinner,typically within the evening quadrant to affect blood glucosemeasurements received by device 600 during the overnight quadrant (e.g.,period of time overnight (e.g., from 22:00 to 04:00)). In someembodiments, tasks are to be performed within the designated part of theday. In some embodiments, tasks can be performed near the designatedpart of the day. In some embodiments, tasks are to be logged within thedesignated part of the day.

In FIG. 6L, device 600 detects tap input 652 a corresponding toselection of selectable task 646 a and tap input 652 b corresponding toselection of selectable task 648 a. As shown in FIG. 6M, in response toreceiving tap inputs 652 a and 652 b, device 600 displays, ontouchscreen display 602, selectable task 646 a and selectable task 648 ahaving check marks as a confirmatory indication that each task has beenselected. Upon selection of the tasks, device 600 displays selectableaffordances “LEARN MORE” and “EXAMPLES” below selected tasks 646 a and648 a. In some embodiments, selection of the “LEARN MORE” affordancecauses device 600 to display additional information pertaining to theselected task. In some embodiments, selection of the “EXAMPLES”affordance causes device 600 to display one or more examplescorresponding to the selected task (e.g., go for a walk after dinner;bike ride before dinner; opt for a low-carb dessert before bed; forgodessert). Upon selecting tasks 646 a and 648 a, device 600 displayscontinue affordance 642 a (which reads, “SELECT 2 ACTION ITEMS”). Device600 detects tap input 654 corresponding to selection of continueaffordance 642 a, which completes action phase set up.

In response to receiving tap input 654 to complete action phase set up,device 600 displays progress user interface 656, as shown in FIG. 6N.Device 600 also displays progress tab affordance 616 c for navigating toprogress user interface 656. Progress user interface 656 includescounter 656 a, which has a live count for the number of tasks completed(e.g., “ACTION ITEMS COMPLETED”), currently showing “0” and the numberof days remaining, currently showing “7”. The action phase for theglucose monitoring feature is a predetermined period of time (e.g., 7days, 10 days), as indicated by the number of days remaining.

Progress user interface 656 of FIG. 6N also includes an evening region658 and a portion of overnight region 660. Each region containsinstructional text for when to perform the selected task. Evening region658 shows selected task 646 a “TRY AN ACTIVITY AROUND DINNER” along withinstructions for tracking and selectable affordances “LEARN MORE” and“EXAMPLES”. Overnight region 660 contains elements analogous to those ofevening region 658. In some embodiments, device 600 detects a swipeinput to scroll the displayed progress user interface 656 and displaysthe entire evening region 658. Device 600 detects tap input 662corresponding to selection of hours tab affordance 616 a and, inresponse, navigates to hourly log user interface 610 similar to thatshown in FIG. 6G and FIG. 6O.

In FIG. 6O, a few days have passed and the current date is August 14, asindicated above device 600. In some embodiments, device 600 displayshourly log user interface 610 with chart region 612 b including thecurrent time (e.g., 20:00) along the x-axis. In some embodiments, device600 detects a swipe input to scroll chart region 612 b to display bloodglucose data collected at an earlier time. In this example, device 600displays hourly log user interface 610 with chart region 612 b showingchart line 612 c from approximately 09:30 to 16:00. Meal glyph 612 fcorresponds to “BAGEL” log entry 614 f. Device 600 detects tap input 664corresponding to selection of activity logging affordance 614 b.

In response to receiving tap input 664 at activity logging affordance614 b, device 600 initiates logging of an activity, as shown by logentry creation user interface 618 in FIG. 6P. As discussed withreference to FIG. 6D, log entry creation user interface 618 includesselectable affordances corresponding to various activities (e.g.,relaxing, walking, running). Device 600 detects tap input 666 a atwalking affordance 620 c, followed by tap input 666 b at next affordance618 e. In response to receiving tap inputs 666 a and 666 b, device 600displays task confirmation user interface 668, as shown in FIG. 6Q.

FIG. 6Q illustrates device 600 displaying, on touchscreen display 602,task confirmation user interface 668. Task confirmation user interface668 is presented while creating a log entry after tasks to be performedduring the action phase have been selected, as shown in FIGS. 6I-6N.Task confirmation user interface 668 includes task 646 a (which reads,“TRY AN ACTIVITY DURING DINNER”) and task 648 a (which reads, “AVOIDHIGH CARB FOODS OR BEVERAGES BEFORE BED”), both of which were selectedduring task selection described with reference to FIGS. 6I-6N. In someembodiments, multiple tasks (e.g., three or more) are presented in taskconfirmation user interface 668. In some embodiments, task confirmationuser interface 668 presents the task corresponding to the time specifiedon log entry creation user interface 618 (e.g., present task 626 a whenthe time specified on log entry creation user interface 618 is between16:00 and 22:00) and does not present task(s) that do not correspond tothe time specified. In some embodiments, device 600 forgoes displayingtask confirmation user interface 618 when the time specified on logentry creation user interface 618 does not correspond to the part of theday for performing a selected task (e.g., do not display taskconfirmation user interface 618 for log entries that are not between16:00 and 22:00 or 22:00 and 04:00). In some embodiments, device 600displays task confirmation user interface 618 regardless of the timespecified on log entry creation user interface 618 and tasks can bemarked as completed outside of the part of the day designated forperforming that task (e.g., create a log entry at 20:00 and select task648 a to be performed between 22:00 and 04:00). In some embodiments, inresponse to detecting an input selecting a task to be marked ascompleted outside of the part of the day designated for performing thattask, device 600 displays an informative message that the effect ofperforming that selected task outside of the part of the day designatedfor performing that task is inconclusive to the physiological datacollected (e.g., “The effects of your logged entry ”avoid high carbfoods or beverages before bed “at 20:00 are inconclusive for yourovernight blood glucose measurements”).

In the example detailed in FIG. 6Q, device 600 detects tap input 670 acorresponding to selection of task 646 a. In some embodiments, inresponse to selection of task 646 a, task 646 a is shown with a checkmark indication. Device 600 also detects tap input 670 b correspondingto selection of save affordance 668 a. In response to receiving tapinput 670 b, device 600 saves the activity log entry and displays hourlylog user interface 610.

As shown in FIG. 6R, device 600 displays, on touchscreen display 602,hourly log user interface 610 with an updated chart region 612 b. Theupdated chart region 612 b shows the period of time ranging from 15:30to 22:00 with chart line 612 c and activity glyph 612 g. Activity glyph612 g corresponds to “WALKING” log entry 614 g. “WALKING” log entry 614g includes an indication that task 646 a was satisfied by walking at20:00. In contrast, “BAGEL” log entry 614 f does not satisfy auser-selected task, and therefore does not include an indication similarto that of “WALKING” log entry 614 g. Device 600 receives tap input 672corresponding to selection of progress tab affordance 616 c, and inresponse, displays progress user interface 656, as shown in FIG. 6S.

As shown in FIG. 6S, device 600 displays, on touchscreen display 602,progress user interface 656, similar to that described with respect toFIG. 6N. While FIG. 6N illustrates progress user interface 656 on thefirst day of the action phase (e.g., after completing action phase setup, August 11), FIG. 6S shows progress user interface 656 during theaction phase (e.g., on August 14). Counter 656 a is updated to show thatfive action items (e.g., tasks) have been completed and there are threemore days in the action phase to perform the tasks displayed on progressuser interface 656.

In FIG. 6S, the evening region 658 includes selected task 646 a, alongwith “WALKING” log entry 614 g and “BIKING” log entry 614 h,corresponding to log entries that satisfied task 646 a of “TRY ANACTIVITY AROUND DINNER.” Log entries 614 g and 614 h include elevationvalues to indicate the impact of performing the activity (e.g., walking,biking) on blood glucose measurements received by device 600 during theevening period (e.g., from 16:00 to 22:00) of the day the activity wasperformed (e.g., walking on August 14, biking on August 13). Incomparison to the typical evening elevation score of “7,” received bydevice 600 during the baseline phase, walking and biking both caused adecrease in evening elevation score (e.g., to “3”, to "2") for theirrespective days. Device 600 receives swipe input 674 corresponding to arequest to scroll progress user interface 656 to view more of overnightregion 660.

As shown in FIG. 6T, in response to swipe input 674, device 600 displaysmore of progress user interface 656, which now shows a portion ofevening region 658 that includes “BIKING” log entry 614 h and all ofovernight region 660. Overnight region 660 includes information similarto that described with respect to in FIG. 6N, including task 648 a, andfurther includes log entries (e.g., “SUGAR FREE CHEESECAKE,” “LOW CARBOATMEAL COOKIE,” “WATER WITH DINNER,”) that correspond to performingtask 648 a.

Device 600 receives tap input 676 corresponding to selection of “BIKING”log entry 614 h. As shown in FIG. 6U, in response to detecting tap input676, device 600 displays, on touchscreen display 602, log detail userinterface 678. Log detail user interface 678 includes details about“BIKING” log entry 614 h, including the date and time the activity wasperformed (e.g., 18:30 on August 13) and the elevation value for bloodglucose measurements received by device 600 during the evening period(e.g., from 16:00 to 22:00) on August 13. Log detail user interface 678also includes selected task 646 a and the typical evening elevationscore of “7.”

In FIG. 6U, log detail user interface 678 shows comparison region 678 a.Comparison region 678 a includes a chart having evening baseline graph634 a overlaid on (e.g., superimposed onto, displayed concurrently with)biking graph 678 b. As previously described with respect to FIG. 6J,evening baseline graph 634 a is a graphical representation of bloodglucose measurements received by device 600 during an evening period(e.g., from 16:00 to 22:00) during the baseline phase. Biking graph 678b is a graphical representation of blood glucose data received by device600 during the evening period on August 13 and includes an activityglyph at 18:30 to show when task 646 a was performed. Evening baselinegraph 634 a and biking graph 678 b both include portions that arevisually distinct (e.g., thicker line weight) from the rest of thegraph. The visually distinct portions of each graph represent bloodglucose measurements that are above a predetermined threshold and areconsidered to be elevated measurements.

Log detail user interface 678 includes selectable exit affordance 678 c.Device 600 detects tap input 680 corresponding to selection of exitaffordance 678 c, and in response, device 600 ceases display of logdetail user interface 678 and displays progress user interface 656, asshown in FIG. 6V.

In FIG. 6V, device 600 returns to displaying progress user interface656. Progress user interface includes selectable plus affordance 660 awithin overnight region 660. Device 600 detects tap input 682corresponding to selection of plus affordance 660 a and, in response,initiates a process for selecting a new task to be performed during theovernight period of time.

As shown in FIG. 6W, in response to receiving tap input 682, device 600displays task addition user interface 684. Task addition user interface684 includes selectable tasks 648 b and 648 c to be performed to affectblood glucose measurements received by device 600 overnight. Tasks 648 band 648 c are the tasks that were not selected during action phase setup, described in further detail with reference to FIGS. 6I-6N. In someembodiments, plus affordance 660 a is not displayed within overnightregion 660, and therefore task addition user interface 684 isunavailable, until the current task (e.g., “AVOID HIGH CARB FOODS ORBEVERAGES BEFORE BED”) has been completed (e.g., performed, logged) anumber of times (e.g., three times). Device 600 detects tap input 686 acorresponding to selection of task 648 c (which reads, “EAT A HIGH FIBERSNACK BEFORE BED”). In some embodiments, in response to receiving tapinput 686 a, device 600 displays task 648 c with an indication that ithas been selected (e.g., with a check mark).

As shown in FIG. 6X, after receiving tap input 686 a, device 600 detectstap input 686 b corresponding to selection of save affordance 684 a. Inresponse to receiving tap input 686 b, device 600 displays progress userinterface 656 having newly selected task 648 c listed in overnightregion 660. Within overnight region 660, task 648 a shows three logentries corresponding to performing “AVOID HIGH CARB FOODS OR BEVERAGESBEFORE BED” and task 648 c shows that no log entries corresponding toperforming “EAT A HIGH FIBER SNACK BEFORE BED” have been completed yet.In some embodiments, after adding a new task, task 648 c is displayed asa selectable option on task confirmation user interface 668 whilecreating a new log entry.

Turning now to FIG. 6Y, the date is currently August 18, seven daysafter starting the action phase, and the current time is 09:00. Device600 displays off boarding notification 688 over hourly log userinterface 610. In some embodiments, off boarding notification 688 isdisplayed over progress user interface. Off boarding notification 688indicates that the action phase is now complete and the next phase(e.g., goal phase) of the glucose monitoring feature is available.Device 600 detects tap input 690 corresponding to selection of continueaffordance 688 a (e.g., “ADD A GOAL”) within off boarding notification688. In response to receiving tap input 690, device 600 initiatescreating a goal in FIG. 6Z.

As shown in FIG. 6Z, device 600 displays, on touchscreen display 602,goal selection user interface 692. Goal selection user interface 692includes selectable tasks 646 a, 648 a, and 648 c, which were performedand tracked during action phase. In some embodiments, tasks aredisplayed on goal selection user interface 692 if the task was completeda number of times (e.g. three times) during the action phase. Device 600detects tap input 694 a corresponding to selection of task 646 a “TRY ANACTIVITY AROUND DINNER.” In some embodiments, in response to receivingtap input 694 a, device 600 displays task 646 a with an indication thatit was selected (e.g., with a check mark). After selection of task 694a, device 600 receives tap input 694 b corresponding to selection ofcontinue affordance 692 a. In response to detecting tap input 694 b,device 600 displays goal customization user interface 696, as shown inFIG. 6AA.

In FIG. 6AA, device 600 displays goal customization user interface 696.Goal customization user interface 696 includes task 646 a along withselectable text fields 696 a and 696 b and day field 696 c forcustomizing the goal based on task 646 a. Text field 696 a correspondsto specifying the activity to be performed (e.g., walking, yoga,running) and text field 696 b corresponds to specifying the duration oftime to perform the activity (e.g., 20 minutes, 60 minutes). Device 600detects tap inputs 698 a and 698 b corresponding to selection of textfields 696 a and 696 b. In some embodiments, in response to receivingtap inputs 698 a and 698 b at text fields 696 a and 696 b forcustomizing the goal, device 600 displays a keyboard for entering thecustom text. Device 600 also detects tap input 698 c corresponding toselection of day field 696 c. In some embodiments, in response toreceiving tap input 698 c at day field 696 c, device 600 shows a listfrom one through seven, for selecting how many times per week to performthe goal. In some embodiments, goal customization user interface 696includes a customization field for specifying when during the recurringsubset of the recurring time period to perform customized goal based ontask 646 a (e.g., after eating dinner, before eating dinner,concurrently with a meal).

In FIG. 6AB, device 600 display goal customization user interface 696having text fields 696 a and 696 b completed to read, “DO YOGA FOR 20MINUTES” and day field 696 c set to “5” times per week. Device 600receives tap input 6100 corresponding to selection of continueaffordance 696 d. In response to detecting tap input 6100, device 600saves customized goal 6102, as shown in FIG. 6AC.

In FIG. 6AC, device 600 continues displaying goal customization userinterface 696 having customized goal 6102 based on task 646 a. Goalcustomization user interface 696 now includes additional selectableaffordances to “EDIT” and “DELETE” customized goal 6102. Goalcustomization user interface 696 further includes selectable addaffordance 696 e. In some embodiments, selecting add affordance 696 ecauses device 600 to display goal selection user interface 692, similarto that shown in FIG. 6Z. Device 600 receives tap input 6104corresponding to selection of save affordance 696 f. In response todetecting tap input 6104, device 600 displays progress user interface656, as shown in FIG. 6AD.

In FIG. 6AD, device 600 displays, on touchscreen display 602, progressuser interface 656 that is updated when in the goal phase. Progress userinterface 656 includes selectable week affordances 656 b and 656 c. Weekaffordance 656 c, corresponding to the current week of “AUG 18-24,” isvisually highlighted (e.g., in bold) to show that it is currentlyselected. Below week affordance 656 c, device 600 displays “0%” toindicate that the goal has not been completed. In some embodiments, inresponse to selection of week affordance 656 b for the week of “AUG11-17,” corresponding to the action phase, device 600 displays weekaffordance 656 b as visually highlighted (e.g., in bold) and includesevening region 658 and overnight region 600 in progress user interface656, as described with reference to FIGS. 6S-6V.

In this example, in FIG. 6AD, when week affordance 656 c is selected,progress user interface 656 includes customized goal 6102 and selectedtask 646 a. Customized goal 6102 includes progress indicators 6102a-6012 e. Progress indicator 6102 a is a plus sign that can be selectedto confirm a completed instance of the customized goal. Progressindicator 6102 e is reads “GOAL” beneath it, to indicate that upon thefifth completed instance of the customized goal, the goal has been metfor the week.

Turning now to FIG. 6AE, the date is currently August 19 and the time is20:00. Device 600 displays progress user interface 656 with customizedgoal 6102 and log entries 614 i and 614 j. In some embodiments, logentries 614 i and 614 j were created via selecting activity loggingaffordance 614 b on hourly log user interface 610, similarly describedwith respect to FIG. 6O. “WALKING” log entry 614 j satisfies task 646 a“TRY AN ACTIVITY AROUND DINNER,” however, it is not performing theactivity of customized goal 6102. In contrast, “YOGA” log entry 614 isatisfies task 646 a and is performing the activity of customized goal6102. In some embodiments, device 600 displays only the log entries thatsatisfy the customized goal (e.g., displays “YOGA” log entry 614 iwithout displaying “WALKING” log entry 614 j). In some embodiments,device 600 displays all log entries that satisfy task 646 a “TRY ANACTIVITY AROUND DINNER” performed during the week of August 18 to August24. Device 600 detects tap input 6106 corresponding to selection ofprogress indicator 6102 a.

As shown in FIG. 6AF, in response to receiving tap input 6106, device600 updates progress indicator 6102 a to show a check mark and updatesprogress indicator 6102 b to the selectable plus sign. Below weekaffordance 656 c, device 600 updates from “0%” to “20%,” indicating thatcustomized goal 6102 has been completed one of five times.

At the end of the week, on August 24 as shown in FIG. 6AG, device 600displays goal review user interface 6108. Goal review user interface6108 includes customize goal 6102 with progress indicators 6102 a-6102 dfilled with a check mark and progress indicator 6102 e empty, to showthat customized goal 6102 was completed four of five times betweenAugust 18 and August 24. Device 600 detects tap input 6110 correspondingto selection of continue affordance 6108 a. In response to receiving tapinput 6110, device 600 displays rating user interface 6112, as shown inFIG. 6AH.

In FIG. 6AH, device 600 displays rating user interface 6112 thatincludes rating region 6114. Rating region 6114 includes a rating scalefrom “0 NOT GOOD” to “10 GREAT” and sliding affordance 6114 a positionedat “5” to start. In some embodiments, sliding affordance 6114 a isinitially positioned at “0 NOT GOOD.” Device 600 detects swipe input6116 corresponding to selection and moving of sliding affordance 6114 a.

As shown in FIG. 6AI, in response to receiving swipe input 6116, device600 moves sliding affordance 6114 a to the left and updates “YOURANSWER” to “7.” Device 600 receives tap input 6118 corresponding toselection of continue affordance 6112 a and, in response, proceeds togoal customization user interface 696.

In FIG. 6AJ, goal customization user interface 696 includes a prompt tomodify customized goal 6102 based on task 646 a using either theselectable edit affordance 696 g or selectable delete affordance 696 h.In some embodiments, selecting edit affordance 696 g causes device 600to display goal customization user interface 696 of FIG. 6AB. In someembodiments, while device 600 is displaying goal customization userinterface 696 of FIG. 6AB for editing the customized goal, device 600receives tap inputs to change (e.g., modify, edit, update) thecustomized goal to be performed during the subsequent period of time(e.g., next week, August 25 to August 31). In some embodiments, inresponse to selection of delete affordance 696 h, device 600 ceasesdisplay of (e.g., deletes, removes) customized goal 6102. Goalcustomization user interface 696 also includes a prompt to add a newgoal using selectable add affordance 696 e. In some embodiments,selecting add affordance 696 e causes device 600 to display goalselection user interface 692, similar to that shown in FIG. 6Z, havingtasks 648 a and 648 b available for selection. In some embodiments,selection of either task 648 a or 648 b initiates goal creation similarto the process described with respect to FIG. 6AA-6AD. In someembodiments, selecting save affordance 696 f causes device 600 todisplay progress user interface 656, similar to the process describedwith respect to FIG. 6AC-6AD.

As shown in FIG. 6AI, device 600 received a rating of “7” for customizedgoal 6102 performed from August 18 to August 24. In some embodiments, ifthe rating is a high range rating (e.g., seven or higher), device 600displays goal customization user interface 696, such as in FIG. 6J. Insome embodiments, if the rating of the customized goal is a mid-rangerating (e.g., from four to six), device 600 displays feedback userinterface 6120, as shown in FIG. 6AK. Feedback user interface 6120 ofFIG. 6AK includes a questionnaire to evaluate success factors forcompleting the customized goal. In some embodiments, if the rating ofthe customized goal is a low range rating (e.g., three or below), device600 displays barrier user interface 6122, as shown in FIG. 6AL. Barrieruser interface 6122 of FIG. 6AL includes a questionnaire directed todetermining barriers (e.g., obstacles) for completing the customizedgoal. In some embodiments, device 600 further displays examples (e.g.,of time management, of ways to maintain motivation) for improving thesuccess and rating of the customized goal. In some embodiments, device600 further displays suggestions (e.g., tips) for improving the successand rating of the customized goal.

FIG. 7 is a flow diagram illustrating a method for logging useractivities during a subset of a recurring time period using anelectronic device in accordance with some embodiments. Method 700 isperformed at a computer system (e.g., 100, 300, 500, 600) that is incommunication with a display generation component (e.g., 602) (e.g., adisplay controller, a touch-sensitive display system; and/or a display(e.g., integrated or connected)) and one or more input devices (e.g.,112, 160, 602) (e.g. gyroscope, accelerometer, microphone, and/or atouch-sensitive surface). Some operations in method 700 are, optionally,combined, the orders of some operations are, optionally, changed, andsome operations are, optionally, omitted.

In some embodiments, the electronic device (e.g., 600) is a computersystem. The computer system is optionally in communication (e.g., wiredcommunication, wireless communication) with a display generationcomponent (e.g., 602) and with one or more input devices (e.g., 112,160, 602). The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. The one or more input devices are configured to receiveinput, such as a touch-sensitive surface receiving user input. In someembodiments, the one or more input devices are integrated with thecomputer system. In some embodiments, the one or more input devices areseparate from the computer system. Thus, the computer system cantransmit, via a wired or wireless connection, data (e.g., image data orvideo data) to an integrated or external display generation component tovisually produce the content (e.g., using a display device) and canreceive, a wired or wireless connection, input from the one or moreinput devices.

As described below, method 700 provides an intuitive way for logginguser activities during a subset of a recurring time period. The methodreduces the cognitive burden on a user for logging user activitiesduring a subset of a recurring time period, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to logging user activities during a subset of arecurring time period faster and more efficiently conserves power andincreases the time between battery charges.

The computer system displays (706), via the display generation component(e.g., 602), a task selection user interface (e.g., 642) with a set ofone or more selectable task user interface objects (e.g., 644, 646,648). The set of one or more selectable task user interface objectsincludes, in accordance with a determination (708) that physiologicaldata (e.g., 634 a) (e.g., data pertaining to blood glucose levels (e.g.,a quantification of elevated blood glucose levels for a duration oftime); baseline blood glucose measurements) for a first subset of arecurring time period (e.g., the time of day that device 600 receiveddata to display line chart 634 a) (e.g., a particular quadrant of timeeach day (e.g., 6 hours of a day, morning, afternoon, evening,overnight); a day (e.g., Monday, Tuesday) within a week)) meets a firstset of criteria (e.g., as illustrated by the elevation value scale of630 a, 634 b). In some embodiments, the first set of criteria includes acriterion that is met when the physiological data exceeds a thresholdvalue (e.g., a blood glucose level exceeds a threshold blood glucoselevel)), a first selectable task user interface object (e.g., 646 a-646c) that corresponds to a first type of user activity (e.g., 646 a (“TRYAN ACTIVITY”), 646 b (“EAT CARBS”), 646 c (“AVOID SNACKS”)) to beperformed during the first subset of the recurring time period (e.g.,the time period specified in 658 of FIG. 6N) (e.g., physical activity(e.g., exercise); eating or drinking certain foods). In someembodiments, in accordance with a determination that physiological datafor the first subset of the recurring time period does not meet thefirst set of criteria, the one or more selectable task user interfaceobjects does not include the first selectable task user interfaceobject. The set of one or more selectable task user interface objectsincludes: in accordance with a determination (710) that physiologicaldata (e.g., the line chart displayed within 636) for a second subset ofthe recurring time period (e.g., the time of day that device 600received data to display the line chart within 636), different from thefirst subset of the recurring time period, meets the first set ofcriteria (e.g., as illustrated by the elevation value scale of 630 a,the elevation value within 636), a second selectable task user interfaceobject (e.g. , 648 a-648 c) that corresponds to a second type of useractivity (e.g., 648 a (“AVOID HIGH CARB FOODS”), 648 b (“TRY SMALLERPORTIONS”), 648 c (“EAT A HIGH-FIBER SNACK”)) (e.g., a type of activitydifferent than the first type of user activity) to be performed duringthe second subset of the recurring time period (e.g., the time periodspecified in 660 of FIG. 6N). In some embodiments, in accordance with adetermination that physiological data for a second subset of therecurring time period meets the first set of criteria, the one or moreselectable task user interface objects does not include the firstselectable task user interface object.

The computer system, while displaying the task selection user interface(e.g., 642), receives (712), via the one or more input devices (e.g.,112, 160), a first set of one or more inputs (e.g., 652 a, 652 b, 654)(e.g., tap inputs).

The computer system, in response to the receiving (714) the first set ofone or more inputs and in accordance with a determination that the firstset of one or more inputs includes an input (e.g., 652 a) selecting thefirst selectable task user interface object (e.g., 646 a), enables (716)logging of (e.g., recording; tracking; logging via user inputs) thefirst type of user activity (e.g., 646 a) during the first subset of therecurring time period (e.g., the time periods specified in 646 and 660of FIG. 6N) (e.g., during future occurrences of the first subset of therecurring time period). The computer system, in response to thereceiving (714) the first set of one or more inputs and in accordancewith a determination that the first set of one or more inputs includesan input (e.g., 652 b) selecting the second selectable task userinterface object (e.g., 648 a), enables (718) logging of the second typeof user activity (e.g., 648 a) during the second subset of the recurringtime period (e.g., as specified in 660). In some embodiments, withoutenabling logging of the first type of user activity during the firstsubset of the recurring time period. Displaying first or secondselectable task user interface objects that correspond to first orsecond user activities based on whether physiological data for differentsubsets of a recurring time period meet a set of criteria provides theuser with feedback about the physiological data for the differentsubsets of the recurring time period. Providing improved visual feedbackto the user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The computer system, prior to displaying the task selection userinterface (e.g., 642), receives (702) (e.g., via one or morephysiological sensors in communication with the computer system (e.g.,integrated into the computer system; in communication with the computersystem); a data transfer from another computer system)) a first set ofphysiological data (e.g., as represented by 612 c) for a firstpredetermined period of time (e.g., from August 1 to August 10 asdescribed with reference to FIGS. 6A-6G) (e.g., 10 days, 14 days, 30days), wherein the physiological data for the first subset of therecurring time period (e.g., the recurring time period is the periodfrom 12PM to 6PM of every day of the predetermined time period) is basedon (e.g., derived from, extrapolated from, extracted from) a subset(e.g., 632 a, 634 a) of the first set of physiological data for thepredetermined time period (e.g., as represented by 612 c from August 1to August 10). In some embodiments, the physiological data is bloodglucose data for the period from 12PM to 6PM for a 10-day datacollection period.

The computer system, after receiving the first set of physiological datafor the first predetermined period of time (e.g., in response tocompleting receiving of the first set of physiological data for apredetermined period of time (e.g., at the end of the predetermined timeperiod)), displays (704) a data summary user interface (e.g., 630) thatincludes a first representation (e.g., 632 a, 632 a) (e.g., a graphicaluser interface object; a representation in a graph; a numerical value)of physiological data of the first set of physiological data for thefirst predetermined period of time that exceeded a first threshold value(e.g., a value below 632 a and 634 b). In some embodiments, the firstrepresentation of physiological data includes an indication of thesubset of a recurring time period (e.g., the 6-hour quadrant of the day)during which the physiological data was obtained). In some embodiments,the data summary user interface includes a second representation ofphysiological data of the first set of physiological data for thepredetermined period of time that exceeded the threshold value. In someembodiments, the second representation of physiological data correspondsto data from a different subset of the recurring time period (e.g., froma different quadrant of the day) than the data that corresponds to thefirst representation of physiological data). Displaying a firstrepresentation of physiological data that exceeded a threshold valueprovides the user with additional feedback as a subset of the receiveddata. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The computer system, wherein prior to receiving (e.g., prior toreceiving all of) the first set of physiological data for the firstpredetermined period of time, the task selection user interface (e.g.,642) is not available for display (e.g., is locked; is not available fordisplay at the request of a user), in response to receiving (e.g.,receiving all of) the first set of physiological data for the firstpredetermined period of time, provides the task selection user interface(e.g., 642) for display (e.g., by displaying notification 626) (e.g.,making the task selection user interface available for display (e.g..,from a previously unavailable state)). In some embodiments, in responseto receiving the first set of physiological data for the predeterminedperiod of time, displaying at least a first interface of a set of userinterfaces that includes the task selection user interface. Providingthe task selection user interface for display in response to the receiptof data controls access to an interface that operates based on whetherthat data is available yet. Performing an optimized operation when a setof conditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the first type of user activity to be performedduring the first subset of the recurring time period is performance of aphysical activity (e.g., 614 g, 614 h) (e.g., exercise) or consumptionof a food or beverage (e.g., the log entries listed below 648 a in FIG.6T) (e.g., eating a meal).

The computer system, after enabling logging of the first type of useractivity during the first subset of the recurring time period and afterenabling logging of the second type of user activity during the secondsubset of the recurring time period, displays a progress user interface(e.g., 656) (e.g., an interface that includes representations ofcompleted user activity(s) that have been enabled for logging) thatincludes, in accordance with a determination that a first instance(e.g., “WALKING” of 614 g, “BIKING” of 614 h) of the first type of useractivity (e.g., 646 a) (e.g., physical activity (e.g., exercise);consumption of food or beverage (e.g., eating carbs last)) has beenlogged during the first subset of the recurring time period (e.g., thetime period specified in 658 of FIG. 6S) (e.g., the recurring timeperiod is the period from 12PM to 6PM of every day), displaying arepresentation (e.g., 614 g, 614 h) (e.g., a user interface object(e.g., a selectable interface object (e.g., an affordance)) thatcorresponds to the first instance of the first type of user activitywithin a first portion (e.g., 658) (e.g., a first third) of the progressuser interface (e.g., a user interface containing all completed actionitems), wherein the first portion of the progress user interfacecorresponds to the first subset of the recurring time period (e.g., theportion dedicated to logged events from 12PM to 6PM of every day).

The computer system, after enabling logging of the first type of useractivity during the first subset of the recurring time period and afterenabling logging of the second type of user activity during the secondsubset of the recurring time period, displays a progress user interface(e.g., 656) (e.g., an interface that includes representations ofcompleted user activity(s) that have been enabled for logging) thatincludes, in accordance with a determination that a first instance(e.g., “SUGAR FREE CHEESECAKE” of FIG. 6T) of the second type of useractivity (e.g., 648 a) (e.g., physical activity (e.g., exercise);consumption of food or beverage (e.g., eating carbs last)) has beenlogged during the second subset of the recurring time period (e.g., thetime period specified in 660 of FIG. 6T) (e.g., the recurring timeperiod is the period from 12PM to 6PM of every day), displaying arepresentation (e.g., the log entry below 648 a in FIG. 6T) (e.g., auser interface object (e.g., a selectable interface object (e.g., anaffordance)) that corresponds to the first instance of the second typeof user activity within a second portion (e.g., 660) (e.g., a firstthird) of the progress user interface (e.g., a user interface containingall completed action items), wherein the second portion of the progressuser interface corresponds to the second subset of the recurring timeperiod (e.g., the portion dedicated to logged events from 12PM to 6PM ofevery day). In some embodiments, the representation of the completeduser activity includes an elevation score. In some embodiments, eachportion of the progress user interface includes the baseline measurementelevation score. In some embodiments, a representation of a secondinstance of first type of user activity is displaying within the firstportion of the progress user interface. Displaying a user interface withrepresentations of completed instances of the user activities organizedby subsets of the recurring time period provides the user with improvedfeedback as to what logged activities have been received by the computersystem during the specific subsets of the recurring time period.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The computer system, after enabling logging of the first type of useractivity during the first subset of the recurring time period, displaysa first representation (e.g., 614 h) (e.g., a user interface object(e.g., a selectable interface object (e.g., an affordance)) of a loggedinstance (e.g., “BIKING” at 18:30) of the first type of user activity(e.g., 646 a).

The computer system receives a first input (e.g., 676) (e.g., a tap)that corresponds to the representation of the logged instance of thefirst type of user activity.

The computer system, in response to receiving the first user input,displays a comparison user interface (e.g., 678) that includes the firstrepresentation (e.g., a graphical user interface object; arepresentation in a graph; a numerical value) of physiological data ofthe first set of physiological data for the first predetermined periodof time that exceeded the first threshold value (e.g., 634 a).

The computer system, in response to receiving the first user input,displays a comparison user interface (e.g., 678) that includes a secondrepresentation (e.g., a graphical user interface object; arepresentation in a graph) of physiological data of a second set ofphysiological data (e.g., data collected during the action phase; datadifferent than the first set of physiological data) that corresponds to(e.g., that was collected in a period of time during which the loggedinstance of the first type of activity was performed) the loggedinstance of the first type of user activity (e.g., 678 b).

The computer system, in response to receiving the first user input,displays a comparison user interface (e.g., 678) that includes a secondrepresentation (e.g., that is graphical similar or identical to thefirst representation) of the logged instance of the first type of useractivity (e.g., the activity glyph along 678 b of FIG. 6U). Displaying auser interface with first and second representations of physiologicaldata for the same subset of a recurring time period provides the userwith feedback as to the state of the data for the same subset of timereceived by the computer system. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The computer system, after the first type of user activity has beenlogged a number of times that exceeds a second threshold value (e.g.,the three logged entries listed below 648 a in FIG. 6V) (e.g.,performing the activity three or more times), displays a firstselectable user interface object (e.g., 660 a) (e.g., a plus button foradding a new user activity).

The computer system receives, via the one or more input devices (e.g.,112, 160), a second set of one or more inputs (e.g., 682, 686 a, 686 b)(e.g., tap inputs), wherein the second set of one or more inputsincludes an input (e.g., 682) corresponding to the first selectable userinterface object (e.g., a tap on the plus button). In some embodiments,the second set of one or inputs includes one or more inputs identifyinga type of user activity to be performed during the first subset of therecurring time period.

The computer system, in response to receiving the second set of one ormore inputs, enables logging of a third type of user activity (e.g., 648c) during the first subset of the recurring time period (e.g., the timeperiod specified in 660 of FIG. 6X). In some embodiments, an actionphase is initiated with two action items to be performed in differentsubsets of the recurring time period, then add a third action item toone of the subsets, so that two or more action items can be performedfor one subset of the recurring time period. In some embodiments, add athird action item for a third subset of the recurring time period (e.g.,the recurring time period is the period from 6PM to 12AM of every day).In some embodiments, user activities (e.g., action items) are the samefor all users (e.g., not personalized). Displaying a selectable userinterface object after a condition is met provides the user withfeedback that additional operations can be performed. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The computer system, after enabling logging of the first type of useractivity during the first subset of the recurring time period, receivesa third set of one or more inputs (e.g., 664, 666 a, 666 b, 670 a, 670b), wherein the third set of one or more inputs includes an input (e.g.,664) to initiate a log entry (e.g., in response to 664 at 614 b in FIG.6O) (e.g., an entry corresponding to performance of a user activity(e.g., a physical activity (e.g., exercise); consumption of a food ordrink); an entry corresponding to a current mood or sentiment of auser). In some embodiments, the third set of one or more inputs includesone or more inputs selecting or identifying additional details (e.g.,the type of activity performed, a time at which it was performed; acurrent mood) of the log entry.

The computer system, after receiving the input to initiate the logentry, displays a selectable confirmation user interface object (e.g.,646 a, 648 a as shown on 668 of FIG. 6Q) for the first type of useractivity.

The computer system, after receiving the input to initiate the log entryand in response to receiving the third set of one or more inputs, inaccordance with a determination that the third set of one or more inputsincludes selection (e.g., 670 a) of the selectable confirmation userinterface object for the first type of user activity, logs an instanceof the first type of user activity (e.g., 614 g).

The computer system, after receiving the input to initiate the log entryand in response to receiving the third set of one or more inputs, inaccordance with a determination that the third set of one or more inputsdoes not include selection selectable confirmation user interface objectfor the first type of user activity, logs an event that is not aninstance of the first type of user activity (e.g., similar to the“BAGEL” log entry of FIG. 6R). In some embodiments, logging an instanceof the first type of user activity includes displaying a selectable userinterface object having an indication that the first type of useractivity was completed. In some embodiments, logging an event includesdisplaying a selectable user interface object that does not include anindication that the first type of user activity was completed. In someembodiments, the selectable user interface objects corresponding toinstances and events are editable. In some embodiments, the selectableuser interface objects corresponding to events are only displayed in theHours tab and not displayed on the Progress tab. In some embodiments,the selectable user interface objects corresponding to instances of thefirst type of user activity are displayed on both the Hours tab and theProgress tab. In some embodiments, initiating a log entry includesdocumenting the time of day. In some embodiments, if the first type ofuser activity is performed during a time that is not the designatedsubset of a recurring time period, log an instance of the first type ofuser activity that includes an indication that the impact of performingthe first type of user activity is inconclusive (e.g., action impactsglucose measurements for the specified subset of recurring time).

In some embodiments, enabling logging of the first type of user activityduring the first subset of the recurring time period includes enablinglogging of the first type of user activity during the first subset ofthe recurring time period for a second predetermined period of time(e.g., as represented by “DAYS REMAINING” in 656 a, from August 11 toAugust 18 as described with reference to FIGS. 6H-6X) (e.g., 7 days, 14days). In some embodiments, after the second predetermined period oftime, at least one function for logging the first type of activitybecomes disabled.

The computer system, after the second predetermined time period ends,provides a goal creation user interface (e.g., 692) for display (e.g.,making a goal creation user interface available for display (e.g., froma previously unavailable state)), wherein the goal creation userinterface is unavailable for display prior to completion of the secondpredetermined period of time. In some embodiments, the goal creationuser interface is an interface that corresponds to method 800. Providinga goal creation user interface for display after a predetermined timeperiod ends permits access to the interface at a point in time when thefunction of the interface is relevant. Performing an optimized operationwhen a set of conditions has been met without requiring further userinput enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7 ) are also applicable in an analogous manner tothe methods described below. For example, method 800 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 700. For example, the goal creation userinterface of method 800 displays a set of one or more selectable goalcreation user interface objects, wherein the set of one or moreselectable goal creation user interface objects are based on the loggingof the type of user activity during the first subset of the recurringtime period as in method 700. For brevity, these details are notrepeated below.

FIGS. 8A-8B are a flow diagram illustrating a method for logging useractivities during a subset of a recurring time period using anelectronic device in accordance with some embodiments. Method 800 isperformed at a computer system (e.g., 100, 300, 500, 600) (e.g., a smartphone, a smart watch) that is in communication with a display generationcomponent (e.g., 602) (e.g., a display controller, a touch-sensitivedisplay system; and/or a display (e.g., integrated or connected)) andone or more input devices (e.g., 160) (e.g. gyroscope, accelerometer,microphone, and/or a touch-sensitive surface). Some operations in method800 are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 800 provides an intuitive way for logginguser activities during a subset of a recurring time period. The methodreduces the cognitive burden on a user for logging user activitiesduring a subset of a recurring time period, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to logging user activities during a subset of arecurring time period faster and more efficiently conserves power andincreases the time between battery charges.

The computer system displays (802), via the display generation component(e.g., 602), a goal creation user interface (e.g., 692, 696) with a setof one or more selectable goal creation user interface objects (e.g.,646 a, 648 a, 648 c). The set of one or more selectable user interfaceobjects includes, in accordance with a determination (804) that a firsttype of user activity (e.g., the activity described with respect to 646a) (e.g., physical activity (e.g., exercise); eating or drinking certainfoods) performed for a first subset of a recurring time period (e.g.,the time period specified in 658 of FIG. 6S) (e.g., a particularquadrant of time each day (e.g., 6 hours of a day, morning, afternoon,evening, overnight); a day (e.g., Monday, Tuesday) within a week)) meetsa first set of criteria (e.g., the criteria discussed at FIG. 6Z), afirst selectable goal creation user interface object (e.g., 646 a) thatcorresponds to the first type of user activity to be performed duringthe first subset of the recurring time period. In some embodiments, thefirst set of criteria includes a criterion that is met when the firsttype of user activity was performed more than a threshold number oftimes. In some embodiments, the first set of criteria includes acriterion that is met when the first type of user activity is determinedto have had a positive effect on physiological data. In someembodiments, in accordance with a determination that the first type ofuser activity performed for the first subset of the recurring timeperiod did not meet the first set of criteria, the one or moreselectable goal creation user interface objects does not include thefirst selectable goal creation user interface object. In someembodiments, the first type of user activity performed for the firstsubset of the recurring time period was logged according to the methodof 700. In some embodiments, the first set of criteria includes acriterion that is met when the first type of user activity has beenavailable for a predetermined time period (e.g., a week, the duration ofthe action phase). In some embodiments, the goal creation user interfacebecomes available after the predetermined time period ends. The set ofone or more selectable user interface objects includes, in accordancewith a determination (806) that a second type of user activity (e.g.,the activity described with respect to 648 a) performed for a secondsubset of a recurring time period (e.g., the time period specified in660 of FIG. 6T), different from the first subset of the recurring timeperiod, meets a first set of criteria (e.g., the criteria discussed atFIG. 6Z), a second selectable goal creation user interface object (e.g.,648 a) that corresponds to the second type of user activity (e.g., atype of activity different than the first type of user activity) to beperformed during the second subset of the recurring time period.

The computer system, while displaying the goal creation user interface(e.g., 692), receives (818) a first set of one or more inputs (e.g., 694a, 694 b, 698 a, 698 b, 698 c) (e.g., taps).

The computer system, in response to the receiving (820) the first set ofone or more inputs and in accordance with a determination that the firstset of one or more inputs includes an input (e.g., 646 a) selecting thefirst selectable goal creation user interface object (e.g., 646 a),enables (822) logging (e.g., recording; tracking; logging via userinputs) of the first type of user activity during the first subset ofthe recurring time period (e.g., during future occurrences of the firstsubset of the recurring time period) for a predetermined duration oftime (e.g., 656 c) (e.g., a week, 10 days).

The computer system, in response to the receiving (820) the first set ofone or more inputs and in accordance with a determination that the firstset of one or more inputs includes an input selecting the secondselectable goal creation user interface object (e.g., a tap at 648 a inFIG. 6Z), enables (824) logging of the second type of user activityduring the second subset of the recurring time period for thepredetermined duration of time (e.g., 656 c). In some embodiments,without enabling logging of the first type of user activity during thefirst subset of the recurring time period. Displaying first or secondselectable goal creation user interface objects based on whether a firstor second type of activity was performed provides the user with feedbackas to what types of activities were previously performed. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the goal creation user interface (e.g., 696)includes (808) (e.g., concurrently, non-concurrently) a set (810) of oneor more selectable user interface objects (e.g., 696 a) (e.g., a textfield; selectable predefined options) that, when selected, configure(e.g., identify; detail; set) a subtype (e.g., “YOGA” as discussed atFIG. 6AB) of the first type of user activity (e.g., 646 a). In someembodiments, the goal creation user interface (e.g., 696) includes (808)(e.g., concurrently, non-concurrently) a set (812) of one or moreselectable user interface objects (e.g., 698 b) (e.g., a text field;selectable predefined options) that, when selected, configure (e.g.,identify; detail; set) a time period (e.g., “AROUND DINNER” of 646 a)(e.g., before a meal; after a meal; at the beginning or the end of thefirst subset of the recurring time period) within the first subset ofthe recurring time period (e.g., the time period specified in 658 ofFIG. 6S) during which the first type of user activity is to beperformed. In some embodiments, the goal creation user interface (e.g.,696) includes (808) (e.g., concurrently, non-concurrently) a set (814)of one or more selectable user interface objects (e.g., 696 b) (e.g., atext field; selectable predefined options) that, when selected,configure (e.g., identify; detail; set) a duration (e.g., 20 minutes asdiscussed at FIG. 6AB) (e.g., 30 minutes; 60 minutes) for which thefirst type of user activity is to be performed. Displaying selectableuser interface objects that configure the goal provides the user withadditional control options for customizing the first type of useractivity. Providing additional control options enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the goal creation user interface includes (808) aset (816) of one or more selectable user interface objects (e.g., 696 c)(e.g., a text field; selectable predefined options) that, when selected,configure (e.g., identify; detail; set) a target number of times (e.g.,“5 TIMES” as discussed at FIG. 6AB) (e.g., a goal) that the first typeof user activity is to be performed (e.g., logged as performed) duringthe first subset of the recurring time period for the predeterminedduration of time. Displaying selectable user interface objects thatconfigure the goal provides the user with more control of the device.Providing additional control of the device enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the first set of criteria is satisfied when a useractivity of a given type has been performed (e.g., performed and logged)at least once during a preceding predetermined period of time (e.g., 614g, 614 h, the log entries listed within 660) (e.g., an action phase). Insome embodiments, the first set of criteria are met when physiologicaldata indicates that a user activity of a given type had a target (e.g.,positive) effect on a physiological parameter (e.g., blood glucoselevels). In some embodiments, the goal creation user interface (e.g.,692) includes, for each given type of activity that met the first set ofcriteria, a selectable goal creation user interface object (e.g., 646 a,648 a, 648 c as discussed at FIG. 6Z) for the given type of activitythat met the first set of criteria. In some embodiments, the goalcreation user interface provides goal creation user interface objectsfor all activity types that were performed during an action phase.Displaying a selectable goal creation user interface object for thegiven types of activity that met the first set of criteria provides theuser with additional feedback as specific activities that wereperformed. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The computer system, after enabling logging of the first type of useractivity (e.g., 6102) during the first subset of the recurring time forthe predetermined duration of time, displays a representation (e.g.,6102 a-6102 e) (e.g., an indication; a graphical user interface object)of the target number of times (e.g., “5 TIMES” as discussed at FIG. 6AB)(e.g., a minimum number of times) that the first type of user activity(e.g., 6102) is to be performed during the first subset of the recurringtime period for the predetermined duration of time. In some embodiments,the representation includes an indication of the number of times thatfirst type of user activity has already been completed during thepredetermined time period. In some embodiments, the representation isseven empty circles, each representing a day, that are filled is as thefirst type of user activity is completed. Displaying an indication(e.g., a progress indicator) of progress towards a target number oftimes that the first type of user activity is to be performed during thefirst subset of the recurring time period for the predetermined durationof time provides the user with feedback as to what is required to meetthe target. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The computer system, after enabling logging of the first type of useractivity (e.g., 6102) during the first subset of the recurring time forthe predetermined duration of time and after the end of thepredetermined duration of time (e.g., on August 24 at FIG. 6AG),receives a second set of one or more user inputs (e.g., 6110, 6116,6118) that correspond to feedback (e.g., 6114 a along the rating scaleat FIG. 6AH-6AI) regarding the first type of user activity (e.g.,feedback indicating a user's sentiment and/or assessment of performanceof the first type of user activity during the predetermined duration oftime).

The computer system, after receiving the first set of one or more userinputs (e.g., after selection of 696 g) and, in some embodiments, inaccordance with a determination that the feedback regarding the firsttype of user activity satisfies a first set of feedback criteria (e.g.,the feedback is of a first type (e.g., negative feedback), displays aset of one or more selectable user interface objects (e.g., analogous to696 a, 696 b, and 696 c at FIG. 6AB) (e.g., a text field; selectablepredefined options) that, when selected, modify one or morecharacteristics (e.g.; a target number of times the activity is to beperformed; a duration for which the activity is to be performed) of thefirst type of user activity (e.g., modify for logging during a second,upcoming predetermined period of time). Displaying a set of one or moreselectable user interface objects to modify one or more characteristicsof the first type of user activity provides the user with more controlof the device. Providing additional control of the device enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The computer system, after enabling logging of the first type of useractivity during the first subset of the recurring time for thepredetermined duration of time and after the end of the predeterminedduration of time (e.g., on August 24 at FIG. 6AG), receives the secondset of one or more user inputs (e.g., 6110, 6116, 6118) that correspondto feedback regarding the first type of user activity (e.g., feedbackindicating a user's sentiment and/or assessment of performance of thefirst type of user activity during the predetermined duration of time).

The computer system, after receiving the second set of one or more userinputs (e.g., after selection of 696 e) and, in some embodiments, inaccordance with a determination that the feedback regarding the firsttype of user activity satisfies a first set of feedback criteria (e.g.,the feedback is of a first type (e.g., negative feedback), displays aset of one or more selectable user interface objects (e.g., analogous to648 a and 648 b at FIG. 6Z) (e.g., a text field; selectable predefinedoptions) that, when selected, enables logging of a third type of useractivity, different from the first type of user activity, during thefirst subset of the recurring time period for a second predeterminedduration of time (e.g., a subsequent period of 7 days), after the firstpredetermined period of time. In some embodiments, display differentquestions based on selection of ranking affordance (e.g., what wentwell? What could go better?). In some embodiments, for selection of alow ranking affordance (e.g., 4 or lower), provide tips for overcomingbarriers. In some embodiments, display 6 tips per action item category.In some embodiments, for selection of a high ranking affordance (e.g., 7or higher), do not display tips and proceed to option to modify goal.Displaying a set of one or more selectable user interface objects toenable logging of a third type of user activity provides the user withmore control of the device. Providing additional control of the devicewithout cluttering the UI with additional displayed controls enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The computer system, after enabling logging of the first type of useractivity during the first subset of the recurring time for thepredetermined duration of time, displays a progress user interface(e.g., 656) (e.g., an interface that includes representations ofcompleted user activity(s) that have been enabled for logging), whereinthe progress user interface includes: a first selectable user interfaceobject (e.g., 656 b) that corresponds to the preceding predeterminedperiod of time (e.g., the action phase), that when selected, displaysrepresentations of logged instances of the first type of user activityfor the preceding predetermined period of time (e.g., 614 g, 614 h, thelog entries listed within 660 at FIGS. 6S-6V) (e.g., the first type ofuser activity performed during the first subset of the recurring timeperiod); and a second selectable user interface object (e.g., 656 c)that corresponds to the predetermined duration of time, that whenselected, displays representations of logged instances (e.g. 614 i, 614j) of the first type of user activity for the predetermined period oftime (e.g., the first type of user activity performed during the firstsubset of the recurring time period). Displaying a user interface withselectable user interface objects to view logged activities for apredetermined period of time provides the user with improved feedback asto what logged activities have been received by the computer system.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of logged user activities during a subset of arecurring time period or any other content that may be of interest tothem. The present disclosure contemplates that in some instances, thisgathered data may include personal information data that uniquelyidentifies or can be used to contact or locate a specific person. Suchpersonal information data can include demographic data, location-baseddata, telephone numbers, email addresses, twitter IDs, home addresses,data or records relating to a user's health or level of fitness (e.g.,vital signs measurements, medication information, exercise information),date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content based on the logged user activities during asubset of a recurring time period that is of greater interest to theuser. Accordingly, use of such personal information data enables usersto have calculated control of the delivered content. Further, other usesfor personal information data that benefit the user are alsocontemplated by the present disclosure. For instance, health and fitnessdata may be used to provide insights into a user's general wellness, ormay be used as positive feedback to individuals using technology topursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in theU.S., collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof logging user activities during a subset of a recurring time period,the present technology can be configured to allow users to select to"opt in" or "opt out" of participation in the collection of personalinformation data during registration for services or anytime thereafter.In another example, users can select not to provide data for logginguser activities during a subset of a recurring time period. In yetanother example, users can select to limit the length of time data ismaintained or entirely prohibit the development of a baseline profile.In addition to providing "opt in" and "opt out" options, the presentdisclosure contemplates providing notifications relating to the accessor use of personal information. For instance, a user may be notifiedupon downloading an app that their personal information data will beaccessed and then reminded again just before personal information datais accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

What is claimed is:
 1. A computer system, comprising: a displaygeneration component; one or more input devices; one or more processors;and memory storing one or more programs configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying, via the display generation component, a goal creationuser interface with a set of one or more selectable goal creation userinterface objects, the set of one or more selectable goal creation userinterface objects includes: in accordance with a determination that afirst type of user activity performed for a first subset of a recurringtime period meets a first set of criteria, a first selectable goalcreation user interface object that corresponds to the first type ofuser activity to be performed during the first subset of the recurringtime period; and in accordance with a determination that a second typeof user activity performed for a second subset of a recurring timeperiod, different from the first subset of the recurring time period,meets a first set of criteria, a second selectable goal creation userinterface object that corresponds to the second type of user activity tobe performed during the second subset of the recurring time period;while displaying the goal creation user interface, receiving a first setof one or more inputs; and in response to the receiving the first set ofone or more inputs: in accordance with a determination that the firstset of one or more inputs includes an input selecting the firstselectable goal creation user interface object, enabling logging of thefirst type of user activity during the first subset of the recurringtime period for a predetermined duration of time; and in accordance witha determination that the first set of one or more inputs includes aninput selecting the second selectable goal creation user interfaceobject, enabling logging of the second type of user activity during thesecond subset of the recurring time period for the predeterminedduration of time.
 2. The computer system of claim 1, the one or moreprograms further including instructions for: prior to displaying thetask selection user interface, receiving a first set of physiologicaldata for a first predetermined period of time, wherein the physiologicaldata for the first subset of the recurring time period is based on asubset of the first set of physiological data for the predetermined timeperiod.
 3. The computer system of claim 2, the one or more programsfurther including instructions for: after receiving the first set ofphysiological data for the first predetermined period of time,displaying a data summary user interface that includes: a firstrepresentation of physiological data of the first set of physiologicaldata for the first predetermined period of time that exceeded a firstthreshold value.
 4. The computer system of claim 1, wherein prior toreceiving the first set of physiological data for the firstpredetermined period of time, the task selection user interface is notavailable for display, the one or more programs further includinginstructions for: in response to receiving the first set ofphysiological data for the first predetermined period of time, providingthe task selection user interface for display.
 5. The computer system ofclaim 1, wherein the first type of user activity to be performed duringthe first subset of the recurring time period is performance of aphysical activity or consumption of a food or beverage.
 6. The computersystem of claim 1, the one or more programs further includinginstructions for: after enabling logging of the first type of useractivity during the first subset of the recurring time period and afterenabling logging of the second type of user activity during the secondsubset of the recurring time period, displaying a progress userinterface, wherein the progress user interface includes: in accordancewith a determination that a first instance of the first type of useractivity has been logged during the first subset of the recurring timeperiod, displaying a representation that corresponds to the firstinstance of the first type of user activity within a first portion ofthe progress user interface, wherein the first portion of the progressuser interface corresponds to the first subset of the recurring timeperiod; and in accordance with a determination that a first instance ofthe second type of user activity has been logged during the secondsubset of the recurring time period, displaying a representation thatcorresponds to the first instance of the second type of user activitywithin a second portion of the progress user interface, wherein thesecond portion of the progress user interface corresponds to the secondsubset of the recurring time period.
 7. The computer system of claim 3,the one or more programs further including instructions for: afterenabling logging of the first type of user activity during the firstsubset of the recurring time period, displaying a first representationof a logged instance of the first type of user activity; receiving afirst input that corresponds to the representation of the loggedinstance of the first type of user activity; in response to receivingthe first user input, displaying a comparison user interface thatincludes: the first representation of physiological data of the firstset of physiological data for the first predetermined period of timethat exceeded the first threshold value; and a second representation ofphysiological data of a second set of physiological data thatcorresponds to the logged instance of the first type of user activity;and and a second representation of the logged instance of the first typeof user activity.
 8. The computer system of claim 1, the one or moreprograms further including instructions for: after the first type ofuser activity has been logged a number of times that exceeds a secondthreshold value, displaying a first selectable user interface object;receiving, via the one or more input devices, a second set of one ormore inputs, wherein the second set of one or more inputs includes aninput corresponding to the first selectable user interface object; andin response to receiving the third set of one or more inputs: enablinglogging of a third type of user activity during the first subset of therecurring time period.
 9. The computer system of claim 1, the one ormore programs further including instructions for: after enabling loggingof the first type of user activity during the first subset of therecurring time period, receiving a third set of one or more inputs,wherein the third set of one or more inputs includes an input toinitiate a log entry; after receiving the input to initiate the logentry: displaying a selectable confirmation user interface object forthe first type of user activity; and in response to receiving the thirdset of one or more inputs: in accordance with a determination that thethird set of one or more inputs includes selection of the selectableconfirmation user interface object for the first type of user activity,logging an instance of the first type of user activity; and inaccordance with a determination that the fourth set of one or moreinputs does not include selection selectable confirmation user interfaceobject for the first type of user activity, logging an event that is notan instance of the first type of user activity.
 10. The computer systemof claim 1, wherein enabling logging of the first type of user activityduring the first subset of the recurring time period includes enablinglogging of the first type of user activity during the first subset ofthe recurring time period for a second predetermined period of time. 11.The computer system of claim 10, the one or more programs furtherincluding instructions for: after the second predetermined time periodends, providing a goal creation user interface for display, wherein thegoal creation user interface is unavailable for display prior tocompletion of the second predetermined period of time.
 12. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of acomputer system that is in communication with a display generationcomponent and one or more input devices, the one or more programsincluding instructions for: displaying, via the display generationcomponent, a task selection user interface with a set of one or moreselectable task user interface objects, the set of one or moreselectable task user interface objects includes: in accordance with adetermination that physiological data for a first subset of a recurringtime period meets a first set of criteria, a first selectable task userinterface object that corresponds to a first type of user activity to beperformed during the first subset of the recurring time period; and inaccordance with a determination that physiological data for a secondsubset of the recurring time period, different from the first subset ofthe recurring time period, meets the first set of criteria, a secondselectable task user interface object that corresponds to a second typeof user activity to be performed during the second subset of therecurring time period; while displaying the task selection userinterface, receiving, via the one or more input devices, a first set ofone or more inputs; and in response to the receiving the first set ofone or more inputs: in accordance with a determination that the firstset of one or more inputs includes an input selecting the firstselectable task user interface object, enabling logging of the firsttype of user activity during the first subset of the recurring timeperiod; and in accordance with a determination that the first set of oneor more inputs includes an input selecting the second selectable taskuser interface object, enabling logging of the second type of useractivity during the second subset of the recurring time period.
 13. Amethod, comprising: at a computer system that is in communication with adisplay generation component and one or more input devices: displaying,via the display generation component, a task selection user interfacewith a set of one or more selectable task user interface objects, theset of one or more selectable task user interface objects includes: inaccordance with a determination that physiological data for a firstsubset of a recurring time period meets a first set of criteria, a firstselectable task user interface object that corresponds to a first typeof user activity to be performed during the first subset of therecurring time period; and in accordance with a determination thatphysiological data for a second subset of the recurring time period,different from the first subset of the recurring time period, meets thefirst set of criteria, a second selectable task user interface objectthat corresponds to a second type of user activity to be performedduring the second subset of the recurring time period; while displayingthe task selection user interface, receiving, via the one or more inputdevices, a first set of one or more inputs; and in response to thereceiving the first set of one or more inputs: in accordance with adetermination that the first set of one or more inputs includes an inputselecting the first selectable task user interface object, enablinglogging of the first type of user activity during the first subset ofthe recurring time period; and in accordance with a determination thatthe first set of one or more inputs includes an input selecting thesecond selectable task user interface object, enabling logging of thesecond type of user activity during the second subset of the recurringtime period.